Overview
The Import Financial Targets application allows the user to import monthly store financial targets from a CSV file in a particular format. This topic describes the format the CSV file has to conform to, as well as the operation of the application.
Additional Information
When the application is first loaded, the user is given the opportunity to browse for a CSV file. This CSV file has to be in the same format as the following example. Note that it should not have header rows:
Show Example Row 2005,3,SC118,23200,14200
The following columns should be present:
| Column | Description |
|---|---|
| Year | Specifies the year and month the row is applicable to. Note that this is not the calendar year or month. This is the year number as defined in the date dimension. If for example your year beings in February, January 2007 would belong to Month 12, Year 2006. |
| Month | |
| Store Code | Specifies the store code (i.e. the Store.store_code) for the store. |
| Financial Target | Specifies the financial target sales value for the month. This is the tax exclusive value. |
| Financial Target GP | Specifies the financial GP target value for the month. |
The import will calculate the tax content of the target using default tax rate of the store (i.e. the Store.default_tax_rate column).
Once the report is run, it will show a message saying whether the import has completed successfully.
If values already exist in the database in the date range, but the CSV is sparse, i.e. doesn't contain values for those entries, the report will present the user with the option to:
- Set the targets on the existing rows to ZERO,
- Leave the targets intact, and proceed with importing the other values, or
- Cancel the import completely, making no changes to the database.
Generally option 1 will be appropriate, because the CSV will represent a complete section of data; however in advanced import cases the user might want to merge the CSV with the database data using option 2.